v3.0.2

Compare Source

This is a patch release that fixes a number of bugs discovered in the v3.x.x release.

BUG FIXES:

• helm_release: Fix description field causing inconsistent plan [GH-1648]
• helm_release: Fix plan error when devel = false is set and version is provided [GH-1656]
• helm_release: Fix postrender being run when binaryPath is nil [GH-1649]
• helm_release: Fix shallow clone bug causing nested sensitive values to be redacted in the k8s API [GH-1644]
• provider: Fix namespace override logic in Kubernetes client initialization [GH-1650]
• provider: Restore support for the KUBE_PROXY_URL environment variable [GH-1655]

v3.0.1

Compare Source

This is a hotfix release.

HOTFIX:

• helm_release: Fix state upgrader code to use correct type for "values" attribute. [GH-1638]

v3.0.0

Compare Source

This release migrates ports the provider project from terraform-plugin-sdk/v2 to terraform-plugin-framework [GH-1379]

Please refer to the migration guide.

BREAKING CHANGES:

• Blocks to Nested Objects: Blocks like kubernetes, registry, and experiments are now represented as nested objects.
• List Syntax for Nested Attributes: Attributes like set, set_list, and set_sensitive in helm_release and helm_template are now lists of nested objects instead of blocks
• The new framework code uses Terraform Plugin Protocol Version 6 which is compatible with Terraform versions 1.0 and above. Users of earlier versions of Terraform can continue to use the Helm provider by pinning their configuration to the 2.x version.

FEATURES:

• Add "literal" as a supported type for the set block [GH-1615]

• helm_release: Add support for ResourceIdentity. [GH-1625]

• helm_release: Add set_wo write-only attribute [GH-1592]

ENHANCEMENT:

• helm_release: Add UpgradeState logic to support migration from SDKv2 to Plugin Framework [GH-1633]
• update helm dependency to v3.17.2 [GH-1608]

BUG FIXES:

• helm_release: Fix namespace behaviour for dependency charts in non-default namespaces [GH-1583]

• change set.value && set_list.value to optional instead of required [GH-1572]

v10.1.16

Compare Source

Bug Fixes

• solution logic tries to create kms when encryption set to false (#​932) (2accb1e)

v10.1.15

Compare Source

Bug Fixes

• Improved DA for better user experience - updated catalog config, doc, architecture diagram, and some of the variables description (#​930) (17414c8)

v10.1.14

Compare Source

Bug Fixes

• fix the prefix input variable in the DA to allow null (#​929) (44f82b1)

v10.1.13

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v2.6.14 (#​923) (a664d0a)

v10.1.12

Compare Source

Bug Fixes

• deps: update terraform dependencies (#​922) (2c05bb8)

v10.1.11

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/cbr/ibm to v1.32.4 (#​921) (40ca41f)

v10.1.10

Compare Source

Bug Fixes

• deps: update terraform dependencies (#​919) (c8ccc5e)

v10.1.9

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v2.6.10 (#​918) (a467523)

v10.1.8

Compare Source

Bug Fixes

• deps: update terraform dependencies (#​917) (c6caf11)

v10.1.7

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v2.6.8 (#​915) (015000c)

v10.1.6

Compare Source

Bug Fixes

• remove temporary workaround for timing issue. Upgrading from previous version will see the expected destroy of resource time_sleep.wait_for_cos_bucket_lifecycle. There has no impact to every day services. (#​913) (112439c)

v10.1.5

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v2.6.7 (#​912) (9ba6c19)

v10.1.4

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v2.6.6 (#​911) (b3ed988)

v10.1.3

Compare Source

Bug Fixes

• deps: update terraform dependencies (#​898) (8ebb5bd)

v10.1.2

Compare Source

Bug Fixes

• deps: update terraform ibm to latest for the deployable architecture solution (#​910) (3a2d0bd)

v10.1.1

Compare Source

Bug Fixes

• fixed catalog validation value for new security enforced bucket variations (#​909) (ec66e8c)

v10.1.0

Compare Source

Features

• added 2 new bucket DA variations: Cross-regional bucket (security-enforced) and Regional bucket (security-enforced) (#​908) (95785a6)

v10.0.0

Compare Source

Features

• add fully configurable cross regional bucket DA variations (#​905) (07c1925)

BREAKING CHANGES

• The following variations no longer exist in the DA: Security-enforced cross-region bucket and Fully configurable Regional bucket. Please migrate to use the new variations instead.

v9.1.0

Compare Source

Features

• add fully configurable regional bucket DA (#​906) (6101b1e)

v9.0.8

Compare Source

Bug Fixes

• add support for ca-mon in regional bucket DA (#​907) (aa3db06)

v9.0.7

Compare Source

Bug Fixes

• deps: bump terraform IBM provider to 1.79.2 (#​904) (8d930c7)

v9.0.6

Compare Source

Bug Fixes

• deps: update required terraform IBM provider to >= 1.79.0, < 2.0.0 (#​899) (23d8aef)

v9.0.5

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/secrets-manager/ibm to v2.5.0 (#​896) (403977d)

v9.0.4

Compare Source

Bug Fixes

• deps: update terraform dependencies (#​894) (f17332c)

v9.0.3

Compare Source

Bug Fixes

• deps: update terraform dependencies (#​886) (9cfdf5a)

v9.0.2

Compare Source

Bug Fixes

• remove prereq scripts (#​890) (602c936)

v9.0.1

Compare Source

Bug Fixes

• pass prefix value for bucket DA catalog validation (#​889) (072c4e0)

v9.0.0

Compare Source

(#​887) (6bb43dc)

Features

• Renamed the DA Cloud automation for Cloud Object Storage -> Cloud automation for Object Storage
• Instance DA variation updates:
  • cleanup of features, IAM permissions, diagram etc in ibm_catalog.json
  • removed default value for prefix and added validation
  • supporting documentation for complex inputs updated
  • use_existing_resource_group and resource_group_name have been changed to existing_resource_group_name. DA no longer supports creating group
  • support added for cos-one-rate-plan (was in module but not DA). The input has been renamed cos_plan -> plan
  • cos_instance_name -> instance_name
  • required terraform version updated to >=1.9.0 and cross variable validation added
• Bucket DA variation updates:
  • removed default value for prefix and added validation

BREAKING CHANGES

• The DA no longer supports creating a new resource group. It only supports using existing resource group.
• The default value has been removed from the prefix input. If you were using the default, you should explicitly set prefix back to dev to prevent resources getting destroyed and recreated

v3.1.1

Compare Source

Bug Fixes

• deps: update required ibm provider version to >= 1.79.1, < 2.0.0 (#​193) (4baead8)

v3.1.0

Compare Source

Features

• Updates to trusted-profile-template submodule:
  - identity_crn input has been changed to identities and now supports all identitiy types: user, serviceid and crn. Its also now optional to pass any idenitify.
  - Added support to assign trusted profile template to single accounts using new input account_ids_to_assign (#​189) (d0f234e)

v3.0.0

Compare Source

(#​181) (07e3a80)

Bug Fixes

• added a fix to prevent resources getting destroyed when a trusted profile name is being renamed
  • trusted_profile_policies now has a required attribute called unique_identifier which must have a unique value per policy. It is only used by terraform for building map objects, it is not use for any actual resource naming. Changing this value will cause resources to be recreated.
  • trusted_profile_claim_rules now has a required attribute called unique_identifier which must have a unique value per claim rule. It is only used by terraform for building map objects, it is not use for any actual resource naming. Changing this value will cause resources to be recreated.
  • trusted_profile_links now has a required attribute calledunique_identifier` which must have a unique value per profile link. It is only used by terraform for building map objects, it is not use for any actual resource naming. Changing this value will cause resources to be recreated.

BREAKING CHANGES

• If upgrading from a previous version, you can prevent resources from being recreated if you use the correct value for the new unique_identifier attribute. For example, if you used the following value for trusted profile name: trusted_profile_name = "my-profile" you should use the following naming conventions:

Trusted profile policies

trusted_profile_policies = [
    {
      unique_identifier = "my-profile-0" # use the format of "<trusted profile name>-0" for first item in the list
      ...
      ...
    },
    {
      unique_identifier = "my-profile-1" # use the format of "<trusted profile name>-1" for second item in the list, and so on
      ...
      ...
    }
]

Trusted profile policies

trusted_profile_claim_rules = [
    {
      unique_identifier = "my-profile-0" # use the format of "<trusted profile name>-0" for first item in the list
      ...
      ...
    },
    {
      unique_identifier = "my-profile-1" # use the format of "<trusted profile name>-1" for second item in the list, and so on
      ...
      ...
    }
]

Trusted profile links

trusted_profile_links = [
    {
      unique_identifier = "my-profile-0" # use the format of "<trusted profile name>-0" for first item in the list
      ...
      ...
    },
    {
      unique_identifier = "my-profile-1" # use the format of "<trusted profile name>-1" for second item in the list, and so on
      ...
      ...
    }
]